Ladeon Six
Nemesis Nation
6
   |
Posted - 2012.04.24 23:22:00 -
[1] - Quote
So, here we are with Escalation and I'm still seeing the same issues I posted about back in Crucible. BTW, every Crucible patch after the one that introduced the launcher displayed the same issues, I just had given up on posting about it. :
**
Here's the steps I had performed
1) Run launcher.ex
1a) launcher.exe downloads and updates the launche
1b) Now launcher.exe is broken (16-bit issue): screenshot
2) OK, so I attempt a repair operation, though I know it's probably not going to work
2a) repair.exe breaks on Step 3/7 just as it did ever since the launcher was introduced: logfile
3) Basically now for users such as myself who experience this issue on Win7, we're stuck as we cannot run the launcher, repair tool, or manually apply .patch files shared by a mate (since the launcher doesn't work
4) The workarounds suggested by CCP Sputnik here don't work obviously in this scenario, except for re-installing the full client, which CCP can imagine is a pain, especially for those who have ISP download caps or have a satellite/mobile ISP (fortunately I have a capless ISP but it's still a royal pain to re-install
5) RadioBANITA's workaround here does not apply to this issue, as the launcher is corrupted and hasn't successfully downloaded the launcher patch installer yet
6) The only solution is to have a mate or computer that is not affected, to upload a working copy of the launcher folder, whereupon the launcher would be the correct version, and it would be able to download the EVE patch normally
7) Anyone with protocol content filtering on their software or hardware AV/Firewall still gets the issue where the working launcher is unable to download the patch, noted per the Crucible thread way back
**
Corrupted (NON-WORKING) launcher directory: here
WORKING launcher directory: here (overwrite the corrupted launcher folder in \CCP\EVE\
**
So in conclusion
1) launcher still doesn't update itself correctly on some Win7 machine
2) repair tool fails at 3/7 if launcher got corrupted during patchin
3) protocol content filtering is still and issue causing us to have to disable/lower security settings on our AV/Firewall
4) users are still forced to come up with their own solutions and workaround
Kinda sounds like the Crucible issues still haven't been ironed out, eh? :P |